Cakewalk // Documentation // SONAR X2 // Why use instrument definitions?
Table of Contents Previous Next Index

Instrument definitionsInstrument definition tutorial ► Why use instrument definitions?

The main reason to import or create an instrument definition is so you can use patch names that are specific to the MIDI module you’re using, instead of using generic General MIDI patch names. It’s much easier to find a particular sound on a MIDI module when the actual names of the patches in the current bank of sounds pop up on a list, instead of just the numbers 0 to 127, or General MIDI names like Trumpet. Of course, if you’re only using General MIDI modules, General MIDI patch names might be all you need. You can also rename each MIDI output with the name of the MIDI module it’s connected to. For example, it might be more meaningful to name a MIDI output Roland Sound Canvas instead of MOTU MIDI Express 5. That way, you won’t have to remember that you connected the Sound Canvas to the MOTU MIDI Express output number 5—the name Sound Canvas shows up as an option in the Output field of each MIDI track in SONAR’s Track view. Also if you have an effects processor or module that’s hard to get to in your studio, you may find it convenient to control it from SONAR.

Copyright © 2024 Cakewalk, Inc. All rights reserved
Sitemap | Privacy Policy | Legal